home *** CD-ROM | disk | FTP | other *** search
- Path: netcom.com!bks
- From: bks@netcom.com (Bradley K. Sherman)
- Newsgroups: comp.lang.eiffel,comp.lang.c,comp.lang.c++,comp.object,comp.software-eng
- Subject: Re: OOA [was:Re: Beware of "C" Hackers -- A rebuttal to Bertrand Meyer]
- Message-ID: <bksDpv1r1.qI@netcom.com>
- Date: 14 Apr 96 16:28:12 GMT
- References: <1995Jul3.034108.4193@rcmcon.com> <4kma54$11m@news4.digex.net> <goochb.334.0015B418@rwi.com> <4kr166$1ep@news.nstn.ca>
- Sender: bks@netcom3.netcom.com
- Organization: Remote Fusion Reactor Reverse Entropy Associates
-
- In article <4kr166$1ep@news.nstn.ca>, dbshapco <dbshapco@fox.nstn.ca> wrote:
- ...
- >In a nutshell, any anticipation of the solution domain pollutes analysis, to
- >the worst case in which analysis is nothing more than an alternate way of
- >describing implementation (ditto design). OOP should generate objects which
- >correspond to entities in the problem domain and the relationships suggested
- >by a well defined taxonomy, and the quality of the classes and class
- >hierarchy vary directly with the quality of analysis. Puerile and
- >simplisitic analysis based on inappropriate or forced correspondences usually
- >results in crippled and incomprehensible classes and class hierarchies.
- ...
- Excellent article. Obviously written by a practitioner.
-
- However, well defined taxonomies are not easy to come by. The
- problem is that the taxonomy of the woman on the warehouse floor
- is *not* the same as the taxonomy of the guy in accounts
- receivable which differs yet again from the salesman, ad
- nauseum throughout the customer's organization. Each person
- chops up the flow of work in a different way.
-
- --bks
-